--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Hi Ray,
>
> Maybe try and avoid sending thousands of messages to the Console.  That mechanism was really only intended for debugging.
>
> Also try to have all prints terminated with a new-line.
>
> Are you using the latest Version 4.30l ??
>
> Regards
> TK
>
>
>
>
> ________________________________
> From: himykabibble <jagboy1964@...>
> To: DynoMotion@yahoogroups.com
> Sent: Sunday, February 17, 2013 3:58 PM
> Subject: [DynoMotion] Re: String Not In Valid Format....
>
>
>  
> Tom,
>
> I seem to recall having this problem once before, due to the comm channel getting over-loaded. Is there any way to know that's happening? I know the error is always being thrown from a call to my function that reads a single Persist var, and parses it as an integer. Obviously, my error handling is not adequate, but the root problem is I'm getting a bogus value back from the call, presumably because the board has disconnected. But how do I figure out what's causing that? Right now, if I don't use my pendant (at least not making PCComm calls), everything works OK.
>
> The one major change I made recently was re-instating the MainStatus calls, which I seem to recall was what caused me these problems back in the beginning.
>
> Regards,
> Ray L.
>
> --- In DynoMotion@yahoogroups.com, "himykabibble" wrote:
> >
> > Tom,
> >
> > Well, that doesn't help! :-) It must be coming from one of the c# objects. I'll have to try to find out where it's coming from. I get a board disconnect (which E-Stops the system), then this message comes up. My guess is something I'm doing is gagging the KFlop, and the error message comes from trying to parse and invalid (or likely no) response. I've also just found several of my pendant functions - the ones that use PCComm (for Run, FeedHold, Stop, etc.) - are not working. I seem to have broken something in the communications.
> >
> > Two steps forward, one backwards....
> >
> > Regards,
> > Ray L.
> >
> > --- In DynoMotion@yahoogroups.com, Tom Kerekes wrote:
> > >
> > > Hi Ray,
> > >
> > > I'm not aware of any such error.  What is the exact error message and where does it appear?
> > >
> > >
> > > Regards
> > > TK
> > >
> > >
> > >
> > > ________________________________
> > > From: himykabibble
> > > To: DynoMotion@yahoogroups.com
> > > Sent: Sunday, February 17, 2013 2:19 PM
> > > Subject: [DynoMotion] String Not In Valid Format....
> > >
> > >
> > >  
> > > Tom,
> > >
> > > My latest round of updates seems to have broken something.... If I put any printfs into my DSP code, I get random disconnects, with an error message indicating that a string argument is not in a valid format. I"m sure this is something I'm doing wrong, but I don't have a clue where to look, as I haven't changed any of the code that is causing this (it mostly seems to be induced by my drawbar "driver"). If I simply comment out all printfs, the problem goes away completely.
> > >
> > > Any idea where I should be looking?
> > >
> > > Regards,
> > > Ray L.
> > >
> >
>

 

Tom,

I'm sending VERY few messages to the console, and all end in a newline. The only messages I had in there were in response to a pendant button press, which is a very rare occurrence.

I'm currently using 430j.

Regards,
Ray L.

--- In DynoMotion@yahoogroups.com, Tom Kerekes wrote:
>
> Hi Ray,
>
> Maybe try and avoid sending thousands of messages to the Console.  That mechanism was really only intended for debugging.
>
> Also try to have all prints terminated with a new-line.
>
> Are you using the latest Version 4.30l ??
>
> Regards
> TK
>
>
>
>
> ________________________________
> From: himykabibble
> To: DynoMotion@yahoogroups.com
> Sent: Sunday, February 17, 2013 3:58 PM
> Subject: [DynoMotion] Re: String Not In Valid Format....
>
>
>  
> Tom,
>
> I seem to recall having this problem once before, due to the comm channel getting over-loaded. Is there any way to know that's happening? I know the error is always being thrown from a call to my function that reads a single Persist var, and parses it as an integer. Obviously, my error handling is not adequate, but the root problem is I'm getting a bogus value back from the call, presumably because the board has disconnected. But how do I figure out what's causing that? Right now, if I don't use my pendant (at least not making PCComm calls), everything works OK.
>
> The one major change I made recently was re-instating the MainStatus calls, which I seem to recall was what caused me these problems back in the beginning.
>
> Regards,
> Ray L.
>
> --- In DynoMotion@yahoogroups.com, "himykabibble" wrote:
> >
> > Tom,
> >
> > Well, that doesn't help! :-) It must be coming from one of the c# objects. I'll have to try to find out where it's coming from. I get a board disconnect (which E-Stops the system), then this message comes up. My guess is something I'm doing is gagging the KFlop, and the error message comes from trying to parse and invalid (or likely no) response. I've also just found several of my pendant functions - the ones that use PCComm (for Run, FeedHold, Stop, etc.) - are not working. I seem to have broken something in the communications.
> >
> > Two steps forward, one backwards....
> >
> > Regards,
> > Ray L.
> >
> > --- In DynoMotion@yahoogroups.com, Tom Kerekes wrote:
> > >
> > > Hi Ray,
> > >
> > > I'm not aware of any such error.  What is the exact error message and where does it appear?
> > >
> > >
> > > Regards
> > > TK
> > >
> > >
> > >
> > > ________________________________
> > > From: himykabibble
> > > To: DynoMotion@yahoogroups.com
> > > Sent: Sunday, February 17, 2013 2:19 PM
> > > Subject: [DynoMotion] String Not In Valid Format....
> > >
> > >
> > >  
> > > Tom,
> > >
> > > My latest round of updates seems to have broken something.... If I put any printfs into my DSP code, I get random disconnects, with an error message indicating that a string argument is not in a valid format. I"m sure this is something I'm doing wrong, but I don't have a clue where to look, as I haven't changed any of the code that is causing this (it mostly seems to be induced by my drawbar "driver"). If I simply comment out all printfs, the problem goes away completely.
> > >
> > > Any idea where I should be looking?
> > >
> > > Regards,
> > > Ray L.
> > >
> >
>

--- In DynoMotion@yahoogroups.com, TK <tk@...> wrote:
>
> Then that should not be a problem. I doubt if it is related but please use 4.30l as that has that fix regarding the GetStatus and Token we found.
>
> Regards
> TK
>
> On Feb 17, 2013, at 4:38 PM, "himykabibble" <jagboy1964@...> wrote:
>
> > Tom,
> >
> > I'm sending VERY few messages to the console, and all end in a newline. The only messages I had in there were in response to a pendant button press, which is a very rare occurrence.
> >
> > I'm currently using 430j.
> >
> > Regards,
> > Ray L.
> >
> > --- In DynoMotion@yahoogroups.com, Tom Kerekes wrote:
> > >
> > > Hi Ray,
> > >
> > > Maybe try and avoid sending thousands of messages to the Console. That mechanism was really only intended for debugging.
> > >
> > > Also try to have all prints terminated with a new-line.
> > >
> > > Are you using the latest Version 4.30l ??
> > >
> > > Regards
> > > TK
> > >
> > >
> > >
> > >
> > > ________________________________
> > > From: himykabibble
> > > To: DynoMotion@yahoogroups.com
> > > Sent: Sunday, February 17, 2013 3:58 PM
> > > Subject: [DynoMotion] Re: String Not In Valid Format....
> > >
> > >
> > >
> > > Tom,
> > >
> > > I seem to recall having this problem once before, due to the comm channel getting over-loaded. Is there any way to know that's happening? I know the error is always being thrown from a call to my function that reads a single Persist var, and parses it as an integer. Obviously, my error handling is not adequate, but the root problem is I'm getting a bogus value back from the call, presumably because the board has disconnected. But how do I figure out what's causing that? Right now, if I don't use my pendant (at least not making PCComm calls), everything works OK.
> > >
> > > The one major change I made recently was re-instating the MainStatus calls, which I seem to recall was what caused me these problems back in the beginning.
> > >
> > > Regards,
> > > Ray L.
> > >
> > > --- In DynoMotion@yahoogroups.com, "himykabibble" wrote:
> > > >
> > > > Tom,
> > > >
> > > > Well, that doesn't help! :-) It must be coming from one of the c# objects. I'll have to try to find out where it's coming from. I get a board disconnect (which E-Stops the system), then this message comes up. My guess is something I'm doing is gagging the KFlop, and the error message comes from trying to parse and invalid (or likely no) response. I've also just found several of my pendant functions - the ones that use PCComm (for Run, FeedHold, Stop, etc.) - are not working. I seem to have broken something in the communications.
> > > >
> > > > Two steps forward, one backwards....
> > > >
> > > > Regards,
> > > > Ray L.
> > > >
> > > > --- In DynoMotion@yahoogroups.com, Tom Kerekes wrote:
> > > > >
> > > > > Hi Ray,
> > > > >
> > > > > I'm not aware of any such error. What is the exact error message and where does it appear?
> > > > >
> > > > >
> > > > > Regards
> > > > > TK
> > > > >
> > > > >
> > > > >
> > > > > ________________________________
> > > > > From: himykabibble
> > > > > To: DynoMotion@yahoogroups.com
> > > > > Sent: Sunday, February 17, 2013 2:19 PM
> > > > > Subject: [DynoMotion] String Not In Valid Format....
> > > > >
> > > > >
> > > > > Â
> > > > > Tom,
> > > > >
> > > > > My latest round of updates seems to have broken something.... If I put any printfs into my DSP code, I get random disconnects, with an error message indicating that a string argument is not in a valid format. I"m sure this is something I'm doing wrong, but I don't have a clue where to look, as I haven't changed any of the code that is causing this (it mostly seems to be induced by my drawbar "driver"). If I simply comment out all printfs, the problem goes away completely.
> > > > >
> > > > > Any idea where I should be looking?
> > > > >
> > > > > Regards,
> > > > > Ray L.
> > > > >
> > > >
> > >
> >
> >
>